MDEV-38289: innodb.log_corruption_recovery sporadically fails
authorMarko Mäkelä <marko.makela@mariadb.com>
Thu, 11 Dec 2025 06:22:41 +0000 (08:22 +0200)
committerOtto Kekäläinen <otto@debian.org>
Tue, 13 Jan 2026 19:03:57 +0000 (19:03 +0000)
commit22ceff32c8a798068766bc14afd75840578fce1a
treef9c6d02490f318028e801a7eb973e2122c23b5f5
parentb044c39c333b558973499d44927e7d1fbf87ad3a
MDEV-38289: innodb.log_corruption_recovery sporadically fails

When the test is starting up the server with innodb_force_recovery=1,
there will be messages about the LSN being in the future. The current
LSN is expected to be 12338 plus any number of FILE_CHECKPOINT records
(16 bytes each). We have observed anything up to 12402=12338+16*4 in
our CI systems. To be on the safe side, let us allow up to ten records.

Origin: https://github.com/MariaDB/server/commit/4ee491f1b2eb356e9dc40f388f79b62cfeb13609

Gbp-Pq: Name MDEV-38289-innodb.log_corruption_recovery-failed-sporadically.patch
mysql-test/suite/innodb/r/log_corruption_recovery.result
mysql-test/suite/innodb/t/log_corruption_recovery.test